X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86CE2.BEDF376E@onstor-exch02.onstor.net>; Mon, 11 Feb 2008 11:17:30 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86CE2.BEDF376E"
Content-class: urn:content-classes:message
Subject: RE: Cougar to Bobcat migration strategy document for review
Date: Mon, 11 Feb 2008 11:17:29 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0849651F@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E05C741C3@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar to Bobcat migration strategy document for review
Thread-Index: AchpodZPB1Qz2CcxRe6MoPEft3LLGADOtbRAAAEpzqA=
References: <BB375AF679D4A34E9CA8DFA650E2B04EC247CD@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E05C741C3@onstor-exch02.onstor.net>
From: "Narain Ramadass" <narain.ramadass@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86CE2.BEDF376E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Just one piece of info/clarification here (on Sandrine's comment to
section 11.1):
=20
EricB pointed out last week that the "system show version" command would
provide the MAC address as below:
=20
eng44 CRN1 diag> system show version
=20

chassis
--------
  Chassis Serial num: 0201320020
  Chassis HW revision: A2
  Chassis MAC Addr: 00:07:34:00:24:00  <<<<<<<<<<<<<<<<<<<<<,
=20
=20
The plan was to figure out how the command got the MAC address and check
if the MAC address was being stored somewhere on the clusterDB. Else, we
will correct the procedure to request the user to run this command on
the Bobcat and note down the MAC address. Sripal will be working on this
over the next few days.
=20
Thanx,
Narain.

________________________________

From: Sandrine Boulanger=20
Sent: Monday, February 11, 2008 11:04 AM
To: Sripal Surendiran (HCL); dl-Design Review
Subject: RE: Cougar to Bobcat migration strategy document for review



5.2 Replace "system config copy" by "system copy all -I", because you
don't know what version is on the standby flash

6.5 Need to specify which one is the standby slot since the Cougar is
not posered yet and no led is on

6.6 Power on the Cougar system and bring the system to SSC-PROM>. I
don't know who would do the migration, but we should probably specify
how to connect the SSC console and how to interrupt it in SSC-PROM.

6.7 One should specify to login as"admin" when getting the "login:"
promot, so that one goes directly to the FTI screen

6.7 Note: only run "system config reset" if the Cougar is initialized
but NOT in a cluster. Remove it from the cluster first.

8 Same comment as 6.7 Note

9 Replace Rocket98 by EverON 3.2

11.1 and 11.2 Need to specify one can only get to ssc prom through the
ssc console cable.=20

11.1 Agree with Chris, it's better to check the mac address from the
seep than relying on the label

Appendix C Suggestion 2: if we make it a requirement that the Bobcat has
to be upgraded to 3.2 or later before migrating, then we should not need
to support more than 4 partitions.

=20

Sandrine

=20

________________________________

From: Sripal Surendiran (HCL)=20
Sent: Thursday, February 07, 2008 8:07 AM
To: dl-Design Review
Cc: Sripal Surendiran (HCL)
Subject: Cougar to Bobcat migration strategy document for review

=20

Hi all,

=20

PFA Bobcat to Cougar migration strategy functional specification
document. Please do respond me with your review comments.

=20

Regards,

Sripal.


------_=_NextPart_001_01C86CE2.BEDF376E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16525" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: navy; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: navy; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dnavy link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D889210719-11022008>Just one piece of info/clarification here (on =

Sandrine's comment to section 11.1):</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D889210719-11022008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D889210719-11022008>EricB pointed out last week that the "system =
show=20
version" command would provide the MAC address as =
below:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D889210719-11022008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2>eng44 CRN1=20
diag&gt; system show version</FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><BR><FONT=20
face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2>chassis<BR>--------<BR>&nbsp;=20
Chassis Serial num: 0201320020<BR>&nbsp; Chassis HW revision: =
A2<BR>&nbsp;=20
Chassis MAC Addr: 00:07:34:00:24:00<SPAN =
class=3D889210719-11022008>&nbsp;=20
&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&=
lt;&lt;&lt;,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D889210719-11022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The plan was to figure out how the command got =
the MAC=20
address and check if the MAC address was being stored somewhere on the=20
clusterDB. Else, we will correct the procedure to request the user to =
run this=20
command on the Bobcat and note down the MAC address. Sripal will be =
working on=20
this over the next few days.</FONT></SPAN></DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: #ffffff" face=3DArial =
color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D889210719-11022008><FONT face=3DArial color=3D#0000ff =

size=3D2>Thanx,</FONT></SPAN></DIV>
<DIV><SPAN class=3D889210719-11022008><FONT face=3DArial color=3D#0000ff =

size=3D2>Narain.</FONT></SPAN></DIV>
<DIV><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Sandrine Boulanger =
<BR><B>Sent:</B>=20
Monday, February 11, 2008 11:04 AM<BR><B>To:</B> Sripal Surendiran =
(HCL);=20
dl-Design Review<BR><B>Subject:</B> RE: Cougar to Bobcat migration =
strategy=20
document for review<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">5.2 Replace =
&#8220;system=20
config copy&#8221; by &#8220;system copy all &#8211;I&#8221;, because =
you don&#8217;t know what version is on=20
the standby flash<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">6.5 Need to =
specify=20
which one is the standby slot since the Cougar is not posered yet and no =
led is=20
on<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">6.6=20
</SPAN></FONT><I><SPAN style=3D"FONT-STYLE: italic">Power on the Cougar =
system and=20
bring the system to SSC-PROM&gt;.</SPAN></I> I don&#8217;t know who =
would do the=20
migration, but we should probably specify how to connect the SSC console =
and how=20
to interrupt it in SSC-PROM.<o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">6.7 One =
should specify=20
to login as&#8221;admin&#8221; when getting the &#8220;login:&#8221; =
promot, so that one goes directly=20
to the FTI screen<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">6.7 Note: =
only run=20
&#8220;system config reset&#8221; if the Cougar is initialized but NOT =
in a cluster. Remove=20
it from the cluster first.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">8 Same =
comment as 6.7=20
Note<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">9 Replace =
Rocket98 by=20
EverON 3.2<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">11.1 and 11.2 =
Need to=20
specify one can only get to ssc prom through the ssc console cable.=20
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">11.1 Agree =
with Chris,=20
it&#8217;s better to check the mac address from the seep than relying on =
the=20
label<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Appendix C =
Suggestion=20
2: if we make it a requirement that the Bobcat has to be upgraded to 3.2 =
or=20
later before migrating, then we should not need to support more than 4=20
partitions.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Sandrine<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Sripal=20
Surendiran (HCL) <BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
Thursday, February 07, 2008 8:07 AM<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> dl-Design Review<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Sripal Surendiran =
(HCL)<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Cougar to Bobcat =
migration=20
strategy document for review</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Hi=20
all,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">PFA Bobcat to Cougar =
migration=20
strategy functional specification document. Please do respond me with =
your=20
review comments.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sripal.</SPAN></FONT><o:p></o:p></P></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C86CE2.BEDF376E--
